Using the AEC Data Model API

All the GraphQL queries must be sent to https://developer.api.autodesk.com/aecdatamodel/graphql.

All AEC Data Model API queries require a 3-legged access token. See Get a 3-Legged Token with Authorization Code Grant for instructions on how to obtain a 3-legged access token. Make sure that you specify the following scopes:

data:read data:create data:write

You can execute GraphQL queries by sending a POST request to https://developer.api.autodesk.com/aecdatamodel/graphql. Each request must have an Authorization header, which must be Bearer <YOUR_ACCESS_TOKEN>. For example;

curl -v 'https://developer.api.autodesk.com/aecdatamodel/graphql' \
-X 'POST' \
-H 'Authorization: Bearer AuIPTf4KYLTYGVnOHQ0cuolwCW2a' \
-H 'Content-Type: application/graphql' \
-d '{
      hubs {
        results {
          name
        }
      }
    }'

{
  "data": {
    "hubs" : {
      "results" : [
        {
          "name" : "Autodesk-Forge"
        },
        {
          "name" : "ME-FLC"
        },
        {
          "name" : "ACC-Cloud-Team"
        },
        {
          "name" : "PIM-ME-Release"
        }
      ]
    }
  }
}

The Content-Type header plays a vital role in indicating the request format. When working with the GraphQL API endpoint, the value for the Content-Type header depends on the data format used (as in the cURl code sample as described previously). If the data is sent in GraphQL format, the Content-Type should be set as application/graphql. However, some clients like Axios format the GraphQL query as a JSON object instead as shown in the following code block.

axios({
  method: 'POST',
  url: '<GraphQL endpoint>',
  data: {
    query: `{
      hubs {
        results {
          name
        }
      }
    }`
  }
})

Axios automatically sets the Content-Type header value to application/json.